Social distribution of emergency status

ABSTRACT

A social networking system distributes information related to emergency events. The social networking system provides an interface for users to view information about the users&#39; connections related to the emergency event. The interface allows users to filter the users&#39; connections to search for connections affected by the emergency event. The interface also includes a status indicator for the users and provides a method for providing input to the connections&#39; status.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/400,012, filed Feb. 17, 2012, which is incorporated by reference inits entirety.

BACKGROUND

This invention relates generally to social networking, and in particularto sharing the status of an individual in relation to an emergency.

Emergencies have the potential to affect a large number of people.Emergency responses can be taxing on infrastructures, supplies, and thesocial fabric. While emergency response crews are responding with food,water, and other necessities, individuals in the emergency area attemptto communicate with their friends and loved ones to find out if they areokay. This communication can be crucial not only to relieve loved onesof worry, but also to relay if an individual needs help or is no longeris danger.

Typical methods of communicating with to loved ones includeindividualized messages, such as by phone, or direct message from amobile device. However, these individualized messages are expensive tothe messaging infrastructure as they originate from or are directed tothe emergency area, which may repeat for each of the individual'scontacts and can often cause messaging channels to overload. Anindividual could notify others through use of a social network topropagate the individual's status. However, existing social networks donot have any means of providing a centralized area to communicatedisaster information or to surface disaster information via a stream ornotification to help ensure that a user's information relating to thedisaster is noticed. Such information can be lost in other news eventsrelated to other users.

SUMMARY

A social networking system emergency interface is provided for enablingusers to communicate information to one another regarding status of theusers relative to an emergency. In an embodiment, an emergency eventnode in the social network is created representing the emergency, andusers are identified as being at-risk relative to the emergencyautomatically, by user-initiated actions, or by identification from alist provided by a trusted authority. Users search for connectionsaffected by the emergency and can view an interface about theconnections of the user related to the emergency. The users can shareinformation about a connection's status with one another and initiateconversations about other users relating to the status. The sharedinformation and conversations are used to identify users who areassociated with the emergency event node.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system overview of a social networking system according toan embodiment.

FIG. 2 shows an emergency response interface according to an embodiment.

FIG. 3 is a flowchart for a process of managing emergency responseswithin a social networking system according to an embodiment.

FIG. 4 is an interaction diagram between users and a social networkingsystem according to one embodiment.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION System Overview

FIG. 1 is a system overview of a social networking system according toan embodiment. A social networking system 100 communicates with avariety of user devices 120 across a network 110. The social networkingsystem 100 includes user profiles 102, which can include locationinformation about the users. The user profiles 102 include informationabout users, such as the user's interests, user biographies anddemographic information, user names, and other information about users.Users can also provide content to the social networking system, such asphotos, status messages, news events, and other items. These items maybe stored within the user profiles 102, or may be stored in separatenodes in the social networking system connected to the user profiles102. The social network 104 provides the connection information betweenthe various users and the various nodes in the social network. Thissocial network 104 provides, for example, information about users'relationship to other users and to other social networking entities suchas interests, companies, and others.

The social networking system 100 includes a page server 101 to providecontent to user devices 120. The provided content includes web pagesassociated with user profiles 102, and can also include media, such asphotos, videos, music, and social networking information. The providecontent can also include information about relationships between usersand other social networking information. The page server 101 is theinterface through which the user devices 120 interact with the socialnetworking system 100. Though described as a “page server,” the pageserver 101 may provide content to users via methods other than webpages. Content can be provided in a variety of ways compatible with theuser devices 120. For example the user devices 120 may connect to thesocial networking system 100 using an application on a mobile device, orusing an html browser on a stand-alone desktop or by other means. Inaddition, the user devices may interact with the social networkingsystem 100 through widgets or components on third party servers (notshown).

The social networking system 100 also includes emergency event nodes103. The emergency event nodes 103 provide nodes in the socialnetworking system to associate users to emergency events. Emergencyevents can represent any type of emergency, crisis, disaster, or otherevent for which users may wish to timely communicate their safety. Forexample, an emergency event node could represent a natural disaster suchas a tsunami or hurricane, or a man-made crisis such as a plane crash,or cruise ship running aground.

The emergency event nodes 103 are associated with users who may beimperiled or affected by the emergency or who have been indicated bythemselves or others to be affected by the emergency. The socialnetworking system 100 allows users to distribute status informationabout the users associated with the emergency event nodes 103. The usersdistributing status information can be the associated user or theassociated user's connections. Connections can indicate statusinformation about a user associated with an emergency such as markingthe user safe, or starting a conversation thread about the user'sstatus.

Users can be associated with emergency event nodes 103 by a variety ofways. For example, many emergency event nodes 103 are associated with aspecific location. This location is correlated with location informationknown about users to determine which users are located in the area ofthe emergency event nodes 103 and may therefore be at-risk. Thegeological location and temporal scale can also be adjusted according tothe impact of the emergency. For example, some emergency events arelocated at a specific storefront, such as a hold-up, while other eventsimpact an entire city or region like a flood, earthquake, or poweroutage. User location information can assist in identifying whether theuser is at-risk by the event by using the granularity of the userlocation in conjunction with the granularity of the event. For example,a bank hold-up emergency likely affects users who are specificallyassociated with the bank, such as users who work at the bank or userswho notified the social networking system 100 that the user is at thebank, such as by checking-in to the location, indicating an intent toattend an event at a location, or identifying the location from a userdevice in the social networking system 100. User locations may also bederived using implicit location information, such as by the accessing IPaddress of the last user login. User locations may be derived from theuser's profile information, such as a city in which the user lives orworks. After determining that a user may be at-risk, the user and theuser's connection may be invited to determine whether the user should beassociated with that emergency event node 103. In addition, the socialnetwork may determine at-risk users by using an external list from athird party. For example, when an emergency on a ship or plane isdeclared, the passenger manifest may be provided to the social network,which can identify members of the social networking community who areat-risk using the names and other details of the manifest andcorrelating these names with identifying information in the socialnetwork, such as the name of a user on the social network. Afteridentifying the users who may be at-risk, user input is used todetermine which users to associate with the emergency event nodes 103.

As a use case, when an emergency occurs in a particular area, and theuser's last check-in is within the emergency area, the user isdetermined to be potentially affected by the emergency (at-risk). Amessage is send to the at-risk user to determine whether the at-riskuser is in fact affected by the emergency event. If the user affirms,then the user is associated with the emergency event node 103. In otherembodiments, in addition to the user, connections of the user who areable to view the reason the user is potentially impacted by theemergency are also able to confirm that the user is in fact affected, inwhich case the user is associated with the emergency event 103.

Whether a user or the user's connections view information indicating theuser is at-risk is impacted by the emergency is affected by privacysettings. For example, if the privacy settings on the user's check-inallow only two connections to view that check-in, then only those twoconnections (in addition to the user himself) may view informationassociating the user to the emergency or to indicate the user isassociated with the emergency event node 103.

Further, individual connections may specifically indicate to the socialnetworking system 100 that a user is at-risk or should be associatedwith the emergency event node 103. For example a user may have planned atrip to an area where an emergency was later declared, but the trip maynot have been reported to the social networking system 100. A connectionwho is aware of the trip may indicate to the system that the user isat-risk by the emergency. In all such interactions, the user's privacysettings and preferences are observed by the system.

Though described here as emergency event nodes 104, emergencies may berepresented in a social networking system in a variety of ways. Theemergency event node 104 is described in this disclosure but anymechanism to provide a convenient method of associating users with anemergency event and providing a method for sharing information about theassociated users vis-à-vis an emergency could be used.

Emergency Response Interface

FIG. 2 shows an emergency response interface 200 according to anembodiment. The emergency response interface 200 may be accessed by auser by navigating to a portion of the social networking system 100associated with the emergency event nodes 104. The emergency responseinterface 200 provides an interface for viewing information related toan emergency. In addition, connections can contribute information thatthe connection knows about the status of users associated with theemergency, which information can be dispersed to the other connectionsof the user. The contributed information can be passed to an informationchannel related to the user, such as a newsfeed, highlight feed, statusfeed, user profile, or user timeline. The appearance of the contributedinformation for a particular viewing user is subject to privacy settingsof the user and the contributing user. The contributed information canalso be maintained on the emergency response interface 200 or associatedwith an emergency event node 103.

The emergency response interface 200 includes a search method 201 foridentifying connections of a user in relation to the emergency event.For example, the user can filter a search according to a variety ofmeans, such as by name, current city, school, workplace, hometown,interest, or a group. A group can comprise users who are not necessarilyconnections or friends of one another, for example a tour group, or aschool classroom. The search parameters can be modified by a search box202. The results of the search are the users' connections who fulfillthe filter and search parameters. This listing can be sorted accordingto the likelihood someone is at-risk using the information known by thesystem and can be further personalized according to the informationaccessible by the viewing user. For example, if a search is conducted by“workplace” for an emergency located in New York, the results would listemployees based in the New York campus of the workplace as more likelyto be at-risk than the California campus and therefore appear first inthe list. However, if the system has information that someone from theCalifornia campus is visiting the New York campus, the system may alsotreat that person as at-risk and place this person higher in the sortedresult. In the absence of a search method 201 or as a default, thesystem in one embodiment searches for connections according to theaffinity of the connection to the user. For example, connections can befiltered using a variety of explicit factors, such as whether the useris already associated with the emergency event node, whether a user hasbeen marked safe with respect to the emergency, whether there are anycomments relating to that user and the emergency, and the user's statedlocation. In addition, implicit factors can be used, such as implicitlocation signals (derived e.g. from a user's IP address), whether a userhas been searched for by another user, and the strength of theconnection between the users. In addition, the search method 201 cansearch for connections who have not been associated with the emergencyevent node, but are sorted by the level of risk identified by thesystem.

The connections displayed by the filtering are also affected by privacysettings. A connection who is considered at-risk for an emergency eventmay not be viewable by the user if the view does not have accessprivileges to any information indicating the connection would be at-riskrelating to the emergency. For example, a connection who has checked-into a location, but manages privacy to the check-in to prevent access bythe user to the check-in. When an emergency occurs related to thelocation affecting the check-in location, the connection may be markedby the system as likely at-risk by the emergency. The user is not bepermitted to see the connection as likely at-risk with the emergencyevent, because the user cannot view the information (the check-in) whichcaused the association. As a result, the connection does not appear infilter results which would otherwise include the connection.

In addition to searching, an emergency information box 220 is includedin the emergency response interface 200 to provide information to usersabout responding to the emergency. The emergency information box 220 caninclude, for example, links to resources for responding to theemergency, links to resources to donate time or services to the reliefeffort, and instructions to teach the user about the social networkinginterface 200 for the emergency. Other information related to theemergency and responses to be taken by the user can also be provided invarious embodiments.

Using the search results, several connections 203 of the user aredisplayed. In this example interface, connections 203 Michael, Kyle, andLinda are displayed. The connections are displayed in individualsections in this embodiment, and include a picture associated with theuser. Each connection 203 also has a status indicator 204. The statusindicator 204 indicates whether the connection's status is known by thesocial networking system, as reported by the connection 203 or one ofthe connection's 203 connections. For example, the status indicator 204indicates the connection 203 is “safe” for Michael and Kyle. Where thereis no confirmed status for a connection 203, such as shown for Linda,the status of the connection 203 has not yet been reported by the useror the user's connections. The status indicator 204 may be blank, or thestatus indicator 204 may be an invitation for the user to determine theconnection 203's status and share information that the user knows. Thestatus indicator 204 may also be reflected in a more detailed statusindicator 205, indicating the number of people who have indicated theconnection is safe. In one embodiment, if the connection 203 has privacysettings preventing the viewing user from accessing the information thatwould have indicated the connection 203 was at-risk, the connection 203is not be shown at all. Alternatively, the connection 203 is shownbecause the connection 203 matches the filter, but the connection 203'sranking or at-risk probability is adjusted according to the informationviewable by the viewing user, which may place the connection 203 furtherdown on the sorted results list.

The specific individuals marking the connection safe can also be shown.The individuals shown to the user as marking a connection 203 safe iscontrolled in one embodiment according to privacy settings by each user.For example, if an individual has indicated a privacy setting that theuser may not see any posts from that individual, that individual'sremarks on a connection 203's safety is not shown in the detailed statusindicator 205, but may be shown in the status indicator 204 depending onthe embodiment. For example, if a user marking the connection 203 assafe has indicated a privacy setting that the viewing user cannot seehis actions, the identity of the user marking the connection 203 safewill not be shown in the detailed status indicator 205 but may be shownin the status indicator 204 depending on the embodiment. A mark safe 206option is also included to allow the user to mark the connection 203safe. When marking a user safe using mark safe 206, the user in oneembodiment is also provided privacy settings to control the distributionof that information.

The connection's 203 most recent status update 207 can also be includedin the emergency response interface 200. The status update 207 can bethe most recent update provided to the connection's 203 general profilepage, or can be a status update provided directly to the emergency eventinterface 200 or emergency event node 103. The most recent status update207 can also be affected by the viewing user's access to theconnection's 203 status updates. For example the connection 203 may haveprovided a first more-recent status update with a privacy settingpreventing the viewing user access to the first update, in which casethe viewing user is shown a second update or no update at all. Thoughthe emergency event interface 200 in this figure depicts the connections203 of the user, the interface 200 may also provide an option to updateone's own status relative to the emergency.

Each connection 203 may also have a comment section 209. The commentsection 209 can be used to discuss a connection 203 relative to theemergency. For example, the user may request information about theconnection's 203 status or provide information known about theconnection's 203 status to the system. Using this interface related tothe emergency event, a forum is thus provided for users of the socialnetworking system 100 to communicate information about one another andpropagate safety information. In addition, connections who are known tobe associated with an emergency event and who have not been marked witha safe status indicator 204 can be easily identified for users or anoperator of the social networking system 100 as potentially requiringassistance.

In addition to positively indicating that the user is “safe,” the statusindicator 204 and other objects above are also used in one embodiment toindicate that the user is not safe or in need of help. For example, theuser may indicate that a connection 203 or the user is trapped in alocation or in need of assistance. A conversation can be started incomments 209 to share the needs of the individual. For example a usermay be isolated but able to use a mobile device to broadcast the user'sstatus using the social networking system 100 in search of help.

Emergency Response Processing

FIG. 3 provides a flowchart for a process of managing emergencyresponses within a social networking system according to an embodiment.An emergency event node is created 300 by the system responsive to anemergency. The emergency event node can be indicated by a systemoperator of the social networking system 100. Alternatively, otherentities in the social networking system may be granted permissions togenerate emergency event nodes. These entities vary according toimplementations and can include authorities such as police, governmentexecutives, news agencies, or other trusted entities. In addition, thesocial networking system in one embodiment monitors news articles orother recent events to identify when an emergency event occurs. Afterdetecting the emergency, the emergency may be verified by a systemoperator, or the emergency event node may be created with an option forusers to confirm the automatically detected emergency represents agenuine emergency event.

Using the emergency information and information about the user location,the system next identifies 301 users located in the emergency area.These users are associated with the emergency event nodes as describedabove, and may appear in an emergency event interface 200.

Next, the system requests status 302 from the users associated with theemergency area and the connections to those users and depending onprivacy settings includes other users of the social network (e.g.connections of connections). For example, the request may be pushed uponnext login, may be a pop-up on another page in the social networkingsystem, may be a notification in a mobile device application, or may bean email. The notification method may be adjusted according to theurgency of the emergency. For example, some emergencies are not urgentlytime-sensitive, and for these emergencies the system may requestinformation when the user or a connection of the user next logs in.Other emergencies are more urgent and yield several of these methodspushed to users at once. In addition, when a connection has notified thesystem that the associated user is safe, the system may withdraw moreintrusive notifications to other users where possible.

Upon receipt of information about a user associated with the emergency,the system propagates 303 the status of the user to the user'sconnections. The propagation can be performed by providing theinformation on a page related to the emergency event, such as theemergency event node, or the propagation can be distributed by insertingthe status information into a communications channel such as a newsfeed,a highlight feed, the user's profile, or the user's timeline. Theinformation may further be propagated to any other users who aresubscribed to user.

If no information is received about a user within a period of time, thesystem in one embodiment initiates a call to action 304. The call toaction can include placing the user on a list of missing or affectedpersons by the emergency, contacting authorities associated with theemergency, or reiterating the need for information to the user'sconnections. In addition, the call to action may initiate a pushnotification to the user or the user's close connections requesting astatus update for the user. For example, the push notification caninclude a text message to an associated phone number, a notification toan application on a mobile device, or a pop-up message when logging intothe social network.

FIG. 4 illustrates an interaction diagram between users and a socialnetworking system according to one embodiment. The social networkingsystem 400 receives an event 430 that indicates an area or list ofaffected users. The social networking system indicates user 410 Mark maybe affected by the emergency event 430. Connections 420 are Mark's 410connections who may be concerned for his welfare as a result of theevent 430.

After the event 430, the social networking system 400 provides a request450 to Mark 410 requesting an update to his status relative to the event430. The system may delay to see if Mark 410 responds, or maysimultaneously request 451 an update to Mark's 410 connections 420. Asdiscussed above, the requests 450 and 451 may be communicated to theuser 410 and connections 420 in a variety of ways, such as by providinga indicator on another section of the social networking system, addingthe indicator to a feed, using a mobile phone notification, or othernotification to the users.

In this example, User 420 Larry accesses 452 the emergency event nodeand receives an interface to view information about the emergency, suchas the interface shown in FIG. 2. User 420 Larry provides a message 453to the social networking system 400 through the interface starting aconversation about the user associated with the event 410. In addition,the message can subscribe Larry 420 to further events related to Mark410 and the event 430. By being subscribed to Mark's events, Larry 420will be automatically updated using a news item, highlight, or othernotification of updates to Mark's 410 status after Larry 420 hasprovided information.

Next, in this example, connection 420 Moe requests access 454 to theevent node 400. Moe 420 indicates to the social networking system 400and the event node 430 an update to Mark's 410 status by marking Marksafe 455. The status indication is provided 456 to the user associatedwith the emergency event 410 Mark, and can be provided 457 to any usersubscribed to the event or the user, in this case Larry 420.

Variations

Though described above primarily in relation to physical emergencies,any event causing a need for communication of status among affectedpersons to the affected persons' connections can be used. For example,an emergency may occur virtually, such as an outage of an importantinternet service which may cause a disruption in the affected persons'lives. The users affected by the outage may be identified, for example,by the users' relationship within the social network relative to theinternet service. For example the internet service may maintain a pagewithin the social networking service which users connect to, become fansof, or “like” within the social networking service. These users whoconnect to the service may be presumed to be affected by the outage andmay need to communicate information about the outage to their socialnetwork.

SUMMARY

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a non-transitory, tangible computer readable storagemedium, or any type of media suitable for storing electronicinstructions, which may be coupled to a computer system bus.Furthermore, any computing systems referred to in the specification mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

Embodiments of the invention may also relate to a product that isproduced by a computing process described herein. Such a product maycomprise information resulting from a computing process, where theinformation is stored on a non-transitory, tangible computer readablestorage medium and may include any embodiment of a computer programproduct or other data combination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

What is claimed is:
 1. A computer-implemented method comprising:establishing an emergency event node for an emergency in a socialnetworking system; accessing records for a plurality of users of thesocial networking system; determining a set of at-risk users from theplurality of users as being associated with the emergency event node;requesting a status update relative to the emergency event node from oneor more users connected to one or more at-risk users in the set ofat-risk users; receiving one or more status updates about the one ormore at-risk users; and communicating the status updates about the oneor more at-risk users to one or more other users who have established aconnection with the one or more at-risk users, the communicatingexcluding communication of the status updates to one or more users whodo not have access privileges to information associating the one or moreat-risk users with the emergency event node.
 2. The computer-implementedmethod of claim 1, wherein the emergency event node includes ageographic area, and wherein determining the set of at-risk userscomprises comparing the geographic area of the emergency event node withlocation information associated with the at-risk users.
 3. Thecomputer-implemented method of claim 2, wherein the location informationfor at least one at risk user comprises one or more of: a check-in ofthe at-risk use, user profile information, an intent to attend an eventat a location, and a location identified from a user device.
 4. Thecomputer-implemented method of claim 3, wherein the location identifiedfrom a user device is based on IP address of the last user login.
 5. Thecomputer-implemented method of claim 1, wherein determining a set ofat-risk users from the plurality of users as being associated with theemergency event node comprises, for at least one of the plurality ofusers: querying the user regarding their association with the emergency;receiving confirmation from the user that they are associated with theemergency; and including the user in the set of at-risk users.
 6. Thecomputer-implemented method of claim 1, wherein determining a set ofat-risk users from the plurality of users as being associated with theemergency event node comprises, for at least one of the plurality ofusers: displaying, to one or more connections of the user, a reason whythe user is potentially at risk; receiving, from at least one of the oneor more connections, an indication that the user is at risk; andincluding the user in the set of at-risk users.
 7. Thecomputer-implemented method of claim 1, wherein determining a set ofat-risk users from the plurality of users as being associated with theemergency event node comprises, for at least one of the plurality ofusers: displaying, to one or more connections of the user, a reason whythe user may be at risk; receiving, from at least one of the one or moreconnections, an indication that the user is not at risk; and notincluding the user in the set of at-risk users.
 8. Thecomputer-implemented method of claim 1, wherein the communicating thestatus update comprises distributing the status update in a newsfeedfeed.
 9. The computer-implemented method of claim 1, wherein thecommunicating the status update comprises distributing the status updateusing a push notification.
 10. The computer-implemented method of claim1, further comprising: receiving a request to establish the emergencyevent node, the request comprising a list of persons associated with theemergency, wherein determining the set of at-risk users comprisescomparing the list of persons with identifying information associatedwith the plurality of users of the social networking system.
 11. Acomputer-implemented method comprising: establishing an emergency eventnode in a social networking system; identifying a set of at-risk usersrelative to the emergency event node; associating a status update witheach of the users in the set of at-risk users who are associated withthe emergency event node; providing an interface to a viewing user ofthe social networking system to view information associated with theemergency event node in the social networking system; excluding a userfrom a plurality of users associated with the emergency event node ifthe viewing user does not have access privileges to informationassociating the connection with the emergency event node; filtering theplurality of users; sorting the filtered users, the sorting based inpart on the filtered users' membership in the set of at-risk users; andsending, for display to the viewing user, information about at least aportion of the sorted users, the information including the statusupdates of the sorted users.
 12. The computer-implemented method ofclaim 11, where the filtering is responsive to an input received fromthe viewing user into the interface.
 13. The computer-implemented methodof claim 11, wherein the filtering is based on location informationassociated with the plurality of users.
 14. The computer-implementedmethod of claim 11, wherein the filtering is based on membership in agroup.
 15. The computer-implemented method of claim 11, wherein one ormore of the status updates includes a safety indicator positivelyindicating that the user in the set of at-risk users associated with thestatus update has been identified as safe.
 16. The computer-implementedmethod of claim 15, wherein the filtering is based on the safetyindicator of the plurality of users associated with the emergency eventnode.
 17. The computer-implemented method of claim 11, wherein theinformation for display further includes identification of one or moreconnections that have indicated that the user is safe.
 18. Thecomputer-implemented method of claim 17, wherein at least one additionalconnection is excluded from the information for display to the viewinguser based on a privacy setting of the at least one additionalconnection.
 19. The computer-implemented method of claim 11, wherein theinformation for display further includes one or more comments from oneor more connections of the at-risk user
 20. The computer-implementedmethod of claim 19, wherein at least one comment is excluded from theinformation for display to the viewing user based on a privacy settingof the connection who posted the at least one comment.